git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: catalin.marinas@gmail.com
Cc: git@vger.kernel.org
Subject: StGIT 0.12.1: pulling up to specific commit (tag)
Date: Thu, 8 Mar 2007 11:23:08 +0300	[thread overview]
Message-ID: <200703081123.09281.arvidjaar@mail.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

After update to 0.12 I am a bit lost how to do it.

I have local branch for kernel tree that contains several patches. I do not 
want this tree to be up-to-date with the latest commits upstream, rather I 
need it on (sub-)version basis. But there is apparently no way to say in 
stgit "please pull up to specific commit".

What I did before 0.12 was

git branch b2.6.21-rc3 v2.6.21-rc3
stg pull . b2.6.21-rc3

Now "stg pull" no more accepts branch name; but I cannot figure how to to the 
same using git config. I have:

branch.cooker.merge=stgit
branch.cooker.remote=stgit

then I do

git branch stgit v2.6.21-rc3
stg pull .

This always results in "up to date" message and nothing is actually merged in 
current branch. But if I do

stg pop -a
git pull . stgit

then changes *are* merged as expected

So for now I have a workaround, but it is rather awkward. May be I am doing it 
the wrong way and I should just do "stg pull; git reset" but I had bad 
experience with mixing stgit and git tree/index manipulation commands in the 
past.

TIA

-andrey

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-03-08  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  8:23 Andrey Borzenkov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-08 20:17 StGIT 0.12.1: pulling up to specific commit (tag) Yann Dirson
2007-03-17  8:33 ` Andrey Borzenkov

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=200703081123.09281.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    /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).