Re: StGit metadata grabbing with git clone

From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date: Nov 22, 2006, 23:56 UTC
Message-ID: <200611230056.15795.robin.rosenberg.lists@dewire.com>
In-Reply-To: <20061122213800.GM7201@pasky.or.cz>

onsdag 22 november 2006 22:38 skrev Petr Baudis:

Show 17 quoted lines

> On Wed, Nov 22, 2006 at 09:29:24PM CET, Robin Rosenberg wrote:
> > onsdag 22 november 2006 13:05 skrev Otavio Salvador:
> > > Hello,
> > >
> > > I'm a happy user of stgit together with git to maintain a patch queue
> > > while I or the company team is working on patches that will be send
> > > for merging. Both works great but we're having troubles when we try to
> > > clone a stgit repository.
> > >
> > > When I clone the repository it grab the source but it loses the
> > > metadata. I would like to grab those too. Does anybody has a solution
> > > or a trick how I can do that?
> >
> > You can copy the repo using rsync or scp instead of git-clone or use stg
> > uncommit after the regular clone.
>
> How do you sync them then?

1) Don't. You're supposed to share stgit patches via email.

2) Want to mess try anyway?

At first I was thinking NO!, but then again, it might be "interesting" to try it.

You can publish the state of a branch using git push. This will look like the pu branch in the official Git repo, i.e. a branch whose list of commits get changed completely, rather than being appended to. This could be considered sane, ie. you publish the current state of your work.

You can also pull from a stgitted branch. Still sane, if you wan't to look at somebody else's work.

I mentioned uncommit. I'm not sure that was a wise suggestion. If you wan't to push and pull changes. don't uncommit incomming changes and don't pretend to work on the same patch and you'll probably be just fine. .....