From: Michael Forney <mforney@mforney.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Re: Git usage
Date: Sun, 12 Jan 2025 23:46:51 -0800 [thread overview]
Message-ID: <2SAF996O4TMLC.3JBVYV26KK20E@mforney.org> (raw)
In-Reply-To: <CA+POUVhfovWvmgT7E4tRF23udJ-aM0TDgcTBWnV6e5siVmWuLg@mail.gmail.com>
Paul Lalonde <paul.a.lalonde@gmail.com> wrote:
> Also, is there a reason why git/rebase -i doesn't have a "drop" option? I
> use it frequently when I find myself with a duplicate change from messing
> up my github fork synchronizations.
You can drop a commit by simply deleting the line.
next prev parent reply other threads:[~2025-01-13 8:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 19:55 [9fans] " Paul Lalonde
2025-01-12 20:10 ` Ron Minnich
2025-01-12 20:44 ` Christopher Nielsen
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 [this message]
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=2SAF996O4TMLC.3JBVYV26KK20E@mforney.org \
--to=mforney@mforney.org \
--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).