git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Petr Baudis <pasky@suse.cz>
Cc: Otavio Salvador <otavio@debian.org>, git@vger.kernel.org
Subject: Re: StGit metadata grabbing with git clone
Date: Thu, 23 Nov 2006 00:56:14 +0100	[thread overview]
Message-ID: <200611230056.15795.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20061122213800.GM7201@pasky.or.cz>

onsdag 22 november 2006 22:38 skrev Petr Baudis:
> 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. .....  


  reply	other threads:[~2006-11-22 23:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 12:05 StGit metadata grabbing with git clone Otavio Salvador
2006-11-22 20:29 ` Robin Rosenberg
2006-11-22 21:38   ` Petr Baudis
2006-11-22 23:56     ` Robin Rosenberg [this message]
2006-11-23 10:47 ` Catalin Marinas
2006-11-23 14:31   ` Otavio Salvador

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200611230056.15795.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=otavio@debian.org \
    --cc=pasky@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).