git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rajkumar S" <rajkumars@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Tracking a branch using StGIT
Date: Fri, 15 Sep 2006 17:48:01 +0530	[thread overview]
Message-ID: <64de5c8b0609150518x279e786tc11b85171dcbe899@mail.gmail.com> (raw)
In-Reply-To: <eee551$mtc$1@sea.gmane.org>

On 9/15/06, Jakub Narebski <jnareb@gmail.com> wrote:
> Besides in remotes file you have only specified which remote branch
> is tracked by which local branch. Additionally all but first are marked
> as not-for-merge. There is no place for default branch to merge with.
>
> There was some discussion about moving remotes information into config
> file, including marking tracking branches as read-only, marking default
> branch to merge (or marking branch as for-merge/not-for-merge), marking
> branch as of not fast-forwarding type (like 'pu' in git.git) on the
> _server_ side etc. But it petered out, unfortunately.

Thanks a lot for your comments, I have just put the RELENG_1 line in
the remotes and have RELENG_1 always checked out.

raj

      reply	other threads:[~2006-09-15 12:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15  8:20 Tracking a branch using StGIT Rajkumar S
2006-09-15 10:42 ` Catalin Marinas
2006-09-15 10:58   ` Andy Whitcroft
2006-09-15 11:17   ` Santi
2006-09-15 11:34     ` Rajkumar S
2006-09-15 11:32   ` Rajkumar S
2006-09-15 11:42     ` Jakub Narebski
2006-09-15 11:59       ` Rajkumar S
2006-09-15 12:09         ` Jakub Narebski
2006-09-15 12:18           ` Rajkumar S [this message]

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=64de5c8b0609150518x279e786tc11b85171dcbe899@mail.gmail.com \
    --to=rajkumars@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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).