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

Re: Feature idea : notes to track status of a commit, which remotes it is shared to

From
W. Trevor King <wking@tremily.us>
Date
Feb 19, 2013, 10:30 UTC
Message-ID
<20130219103042.GA4565@odin.tremily.us>
In-Reply-To
<51234801.5050208@mildred.fr>
On Tue, Feb 19, 2013 at 10:38:09AM +0100, Mildred Ki'Lya wrote:
Show 5 quoted lines
> Then, we could have all the history rewriting commands (such as
> rebase or pull --rebase) die when rewriting commits that are already
> published anywhere. We could make an exception for a --force/-f flag
> or configuration option, or commits published in another local
> repository owned by the same user.

You might want to look into extending the sample pre-rebase hook, which prevents topic branches that are already merged to 'next' branch from getting rebased. You'd just have to loop over all remote references instead of only checking the local 'next' branch.

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
Previous: Junio C HamanoNext: W. Trevor King
Message 4 of 5 in “Feature idea : notes to track status of a commit, which remotes it is shared to”
  1. Mildred Ki'LyaFeb 19, 2013
  2. Thomas RastFeb 19, 2013
  3. Junio C HamanoFeb 19, 2013
  4. W. Trevor KingFeb 19, 2013
  5. W. Trevor KingFeb 19, 2013

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.