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

Re: How to track history of personal changes in a repository?

From
MMMatthew McClure <matt@continuousdelta.com>
Date
Aug 29, 2019, 17:55 UTC
Message-ID
<CAEV-cEp19ehfBwHxh7OGsvTxTchNJLSRZGZXqAsDjyQg-W3rFA@mail.gmail.com>
In-Reply-To
<CABPp-BE0ij8zF22xbvjbcq3vG-VwWjUmjNo45Lsm0BEnH=iZ-A@mail.gmail.com>
On Thu, Aug 29, 2019 at 1:04 PM Elijah Newren <newren@gmail.com> wrote:
Show 5 quoted lines
>
> Perhaps put all the changes in a specific branch and run:
>   git config branch.${personalBranchName}.pushRemote
> Do.Not.Push.Changes.From.This.Branch
> ?  (And make sure that push.default is not set to 'matching'.)

I imagine putting all the changes on a specific branch might be part of a solution. I'm looking for ways to keep the changes in the work tree as well, even as I switch among other branches I'm working on.

-- Matthew McClure Continuous Delta https://www.continuousdelta.com/

Previous: Elijah NewrenNext: Elijah Newren
Message 3 of 6 in “How to track history of personal changes in a repository?”
  1. Matthew McClureAug 29, 2019
  2. Elijah NewrenAug 29, 2019
  3. Matthew McClureAug 29, 2019
  4. Elijah NewrenAug 30, 2019
  5. Philip OakleyAug 31, 2019
  6. Matthew McClureSep 3, 2019

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.