[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Requirements gathering for new package source control

On Mon June 9 2008, Jesse Keating wrote:
> These are good, albeit a bit lengthy.  Lets see what we can do here.
> On Mon, 2008-06-09 at 23:12 +0200, Till Maas wrote:
> > I would like to have a way so easily track patches against the cvs state
> > of a package with the possibility to do private commits and an easy way
> > to merge them to the official branch or show them others in a way that
> > they can easily merge them. This would make co-maintaining packages a lot
> > easier imho.
> I think I know what you're talking about here, but I want to clarify.
> You get a copy of the "upstream" frob module.  You then do some local
> changes and even local commits against frob.  You can query upstream
> "frob" to see if anything changed upstream and integrate those into your
> copy.  Eventually you take your local changes and push them 'upstream',
> right?

If upstream here is the Fedora scm, then this is what I mean.


Attachment: signature.asc
Description: This is a digitally signed message part.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]