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

Re: Random Git Issues/Wishlist

From
CMCatalin Marinas <catalin.marinas@arm.com>
Date
Jul 24, 2006, 10:19 UTC
Message-ID
<tnxirln5mqy.fsf@arm.com>
In-Reply-To
<20060723042725.GA12306@spearce.org>
Shawn Pearce <spearce@spearce.org> wrote:
Show 7 quoted lines
> Petr Baudis <pasky@suse.cz> wrote:
>>   (viii) Patches versioning in StGit - many people I've told about StGit
>> complained that it doesn't version patches (and possibly moved to mq?).
>> We should have some scheme for doing meta-history (especially
>> interesting when/if we aim to make altering history easy).
>
> Doesn't StGit now have a single ref for every patch commit?
Yes, it does and the history is lost.
> What about turning on reflog support on those refs and reading the
> reflog for the ``history'' of that patch?  Granted the reflog isn't
> prune proof but it is a history of that ref's values over time.

That's a good idea indeed (I haven't noticed this feature). Anyway, I don't see any problem with not being prune-safe. I wouldn't want to preserve the refresh history of a patch forever. If I have a stable series I want to keep, I either clone it or simply tag it.

I think that people willing to keep the patch history for a number of years (and be prune-safe) should use topic branches rather than StGIT. Patches are meant to be more lightweight than topic branches and might have a shorter life-time. There were some people at the OLS BOF session even mentioning that they don't care about long-term history.

The StGIT feature wish-list after the OLS is:
- patch history (I'll probably use reflogs as you suggested)
- configurable pull command (currently uses git-pull only)
- commit directly to a patch which is not top
- patch synchronisation between between branches (as some people,
  including me have the same patches based on different branches and
  they have scripts for moving the changes in one to the others)
- document the workflow on the StGIT wiki
- maybe a separate undo command rather than passing a --undo option to
  push and refresh
-- 
Catalin
Previous: Shawn PearceNext: Petr Baudis
Message 6 of 7 in “Random Git Issues/Wishlist”
  1. Petr BaudisJul 22, 2006
  2. Paolo CiarrocchiJul 22, 2006
  3. Martin LanghoffJul 23, 2006
  4. Paolo CiarrocchiJul 23, 2006
  5. Shawn PearceJul 23, 2006
  6. Catalin MarinasJul 24, 2006
  7. Petr BaudisSep 23, 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.