9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Git usage
Date: Sun, 12 Jan 2025 14:44:19 -0600	[thread overview]
Message-ID: <CAH7AAvp7MFxGHwjaYtrKkYYZraYX56zBK0_JgTV7b11cU3gACw@mail.gmail.com> (raw)
In-Reply-To: <CAJPCErnDr-thEZwBkZJxNdcgbACXj-H=_6_K=5-x8gRz7=qkoQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]

Like Ron, I also leave my branches around for reference unless I know for
certain I will never have any use for them. That's just my workflow,
though. Others will probably have different ideas.

Chris

On Sun, Jan 12, 2025, 14:14 Ron Minnich <rminnich@p9f.org> wrote:

> with the Linus git, you can
> git push origin :multiboot_magic
> and it's gone.
>
>  Not quite sure about Ori's git.
>
> That's the only way I've done it.
>
> I actually have 540 branches at my u-root fork, so I'm hardly a good
> example. I leave them lying around for reference.
>
> On Sun, Jan 12, 2025 at 11:56 AM Paul Lalonde <paul.a.lalonde@gmail.com>
> wrote:
> >
> > Now that I'm doing some daily development, I'm running into process
> issues with git.  That probably means I'm doing something wrong, and I'm
> hoping someone might disabuse me.
> >
> > My workflow is to sync my github fork of rminnich/nixos, then git/pull
> to get up to date with my repo.  I then make a branch for my work:
> git/branch -b remotes/origin/regen -n some_feature
> > After some time, I commit my changes and git/push.  I can then generate
> the pull request on github and manage the review there, etc, then delete
> the branch on github, then 'git/branch regen && git/branch -d some_feature'
> to clean up my world.
> >
> > This almost works, but leaves a bunch of remotes in my repo:
> >
> > fluxcpu% git/branch -a
> > heads/master
> > heads/fix_multiboot_magic
> > heads/keep
> > heads/_rebase.working
> > heads/fix_mp_init
> > heads/some_feature
> > remotes/origin/master
> > remotes/origin/regen
> > remotes/origin/boots
> > remotes/origin/multiboot_magic
> > remotes/origin/fix_multiboot_magic
> > remotes/origin/fix_mp_init
> >
> >
> > What's the right way to clean up these ever-growing remotes?
> >
> > Paul
> > 9fans / 9fans / see discussions + participants + delivery options
> Permalink

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc30944502958e1a0-M1fa1aff33e0459f051eba634
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 3785 bytes --]

  reply	other threads:[~2025-01-12 20:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-12 19:55 Paul Lalonde
2025-01-12 20:10 ` Ron Minnich
2025-01-12 20:44   ` Christopher Nielsen [this message]
2025-01-12 21:06 ` [9fans] " Paul Lalonde
2025-01-12 21:55   ` Noam Preil
2025-01-12 22:08     ` Paul Lalonde
2025-01-12 22:17       ` Noam Preil
2025-01-12 22:50         ` Paul Lalonde
2025-01-13  0:07           ` ori
2025-01-13  0:14             ` Paul Lalonde
2025-01-13  0:34               ` ori
2025-01-13  0:32   ` ori
2025-01-13  2:22     ` Paul Lalonde
2025-01-13  5:55       ` ori
2025-01-13  5:59       ` ori
2025-01-13  7:46       ` Michael Forney
2025-01-13  0:17 ` [9fans] " ori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH7AAvp7MFxGHwjaYtrKkYYZraYX56zBK0_JgTV7b11cU3gACw@mail.gmail.com \
    --to=cnielsen@pobox.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).