git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Tracking a branch using StGIT

From
RSRajkumar S <rajkumars@gmail.com>
Date
Sep 15, 2006, 12:18 UTC
Message-ID
<64de5c8b0609150518x279e786tc11b85171dcbe899@mail.gmail.com>
In-Reply-To
<eee551$mtc$1@sea.gmane.org>
On 9/15/06, Jakub Narebski <jnareb@gmail.com> wrote:
Show 9 quoted lines
> 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
Previous: Jakub Narebski
Message 10 of 10 in “Tracking a branch using StGIT”
  1. Rajkumar SSep 15, 2006
  2. Catalin MarinasSep 15, 2006
  3. Andy WhitcroftSep 15, 2006
  4. SantiSep 15, 2006
  5. Rajkumar SSep 15, 2006
  6. Rajkumar SSep 15, 2006
  7. Jakub NarebskiSep 15, 2006
  8. Rajkumar SSep 15, 2006
  9. Jakub NarebskiSep 15, 2006
  10. Rajkumar SSep 15, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.