octave-maintainers
[Top][All Lists]
Advanced

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

Re: hggroup available in graphics archive


From: Thomas Weber
Subject: Re: hggroup available in graphics archive
Date: Wed, 30 Apr 2008 09:17:58 +0200

Am Dienstag, den 29.04.2008, 22:07 +0200 schrieb Michael Goffioul:
> On Tue, Apr 29, 2008 at 8:07 PM, John W. Eaton <address@hidden> wrote:
> >  | OK, but it will take time to familiarize with this method.
> >
> >  Yes.  Also, I'm not sure how you would deal with a public or shared
> >  archive that includes the patches when you are using MQ.  If this
> >  isn't covered in the Mercurial docs, then maybe it is a question for
> >  the Mercurial help list.
> 
> That's indeed my fear. Would it still be possible to share a common
> archive and make it public?

MQ patches are not normally part of the published archive. You can
create your own repository with them and indeed there's an option to "hg
qinit" to do just that.

http://hgbook.red-bean.com/hgbookch12.html#x16-29200012.11


> Recently, I tried to use MQ locally. This revealed very handy to work
> on a single patch incrementally, even on multiple development
> setup (I use 2 computers for development): I just had to copy the
> patch between the 2 computers and play with qpop/qpush. In the
> end, I commited a larger, but more atomic, changeset to the
> archive. However, I'm not sure how to deal with that in the context
> of a shared public archive.

I'd say you shouldn't. Keep your patches small, so individual changes
can be pulled. But don't throw away most of the machinery your VCS
offers you, especially when collaborating with others.

        Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]