Topicc
  Home FAQ Contact Sign in
 
Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...

found 7 articles for 0.303 sec
On 2008-06-04, apfelmus <apfelmus@quantentunnel.de> wrote: > Peter Hercek wrote: >> But what about this git rebasing option? How to do it more easily >> (than the solution I know and I described it later) in darcs? >> >> using "git-rebase --onto master next topic" to get from: >> to: >> >> o---o---o---o---o master >> \ >> o---o---o---o---o next >>     

Group: fa.haskell · Group Profile · Search for Topicc in fa.haskell
Author: Aaron Denney
Date: Jun 4, 2008 04:12

On Sat, 1 Mar 2008 12:21:03 +0100, martin f krafft <madduck@debian.org> said: also sprach Manoj Srivastava <srivasta@debian.org> [2008.02.29.2153 +0100]: 3) I propose ./debian/branches/{TopicA,TopicB,TopicC}.diff.gz files. Each diff, applied to the orig.tar.gz , shall recreate for the interested user the corresponding branch in my development. Bingo. With this addition
Show full article (3.32Kb) · Show article thread
* martin f. krafft: > also sprach Manoj Srivastava <srivasta@debian.org> [2008.02.29.2153 +0100]: >> 3) I propose ./debian/branches/{TopicA,TopicB,TopicC}.diff.gz >> files. Each diff, applied to the orig.tar.gz , shall recreate for >> the interested user the corresponding branch in my development. >> >> Bingo. With this addition, every user that want to see where the     

Group: linux.debian.devel · Group Profile · Search for Topicc in linux.debian.devel
Author: Manoj Srivastava
Date: Mar 1, 2008 08:50

also sprach Manoj Srivastava <srivasta@debian.org> [2008.02.29.2153 +0100]: 3) I propose ./debian/branches/{TopicA,TopicB,TopicC}.diff.gz files. Each diff, applied to the orig.tar.gz , shall recreate for the interested user the corresponding branch in my development. Bingo. With this addition, every user that want to see where the integration branch comes from
Show full article (5.80Kb) · Show article thread
* Manoj Srivastava: > Now, a lot of what I need is already present. > 1) the orig.tar.gz represents the upstream branch, exactly. > 2) the diff.gz + orig.tar.gz represents the integration branch, > exactly. > > So the missing thing is the topic branches. > 3) I propose ./debian/branches/{TopicA,TopicB,TopicC}.diff.gz > files. Each diff, applied to the orig.tar     

Group: linux.debian.devel · Group Profile · Search for Topicc in linux.debian.devel
Author: Florian Weimer
Date: Mar 1, 2008 04:40

On Sat, Jan 26, 2008 at 11:39:32PM +0100, Pierre Habouzit wrote: Another thing is that people have the old habit to see the source package be the preferred form of modification for a Debian package. Hmm. This started off a train of thought. In one sense, one could see the source code for the binary package as the sources delivered by applying the diff.gz to the upstream tarball
Show full article (2.03Kb) · Show article thread
When you convert RH to printed documentation (Word), the RH Index frequently points to the wrong pages in this situation: The Table of Contents is organized by books, and "Start each topic on a new page" is not selected. In other words, within a book, topics run on. Both the Index and TOC show some incorrect page numbers when you first look at the output. The TOC is easily corrected     

Group: linux.debian.devel · Group Profile · Search for Topicc in linux.debian.devel
Author: martin f krafft
Date: Mar 1, 2008 03:30

Show full article (2.07Kb) · Show article thread
    

Group: linux.debian.devel · Group Profile · Search for Topicc in linux.debian.devel
Author: Florian Weimer
Date: Feb 29, 2008 13:40

Show full article (0.97Kb) · Show article thread
    

Group: linux.debian.devel · Group Profile · Search for Topicc in linux.debian.devel
Author: Manoj Srivastava
Date: Feb 29, 2008 13:00

Show full article (4.99Kb) · Show article thread
    

Group: macromedia.robohelp.printed_documentation · Group Profile · Search for Topicc in macromedia.robohelp.printed_documentation
Author: HKabaker
Date: May 17, 2007 17:25

Show full article (2.16Kb)