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

Re: Tracking a branch using StGIT

From
RSRajkumar S <rajkumars+git@gmail.com>
Date
Sep 15, 2006, 11:34 UTC
Message-ID
<64de5c8b0609150434r2162042dmcf6b587466f6ab9d@mail.gmail.com>
In-Reply-To
<8aa486160609150417s288d6540tc8ee6aa83bbf67b4@mail.gmail.com>
On 9/15/06, Santi <sbejar@gmail.com> wrote:
Show 6 quoted lines
> No. But the it merge the first pull line in .git/remotes/origin into
> the current branch. So he only has to put the RELENG_1 line the first,
> as:
>
> URL: /usr/local/pfSense/upstream/pfSense/.git
> Pull: refs/heads/RELENG_1:refs/heads/RELENG_1
Thanks a lot, that should solve this.
raj
Previous: SantiNext: Rajkumar S
Message 5 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.