From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH 1/6] git: document git/import -n
Date: Thu, 28 Sep 2023 00:10:53 -0700 [thread overview]
Message-ID: <096F8BC706832E96037C1D4F7E8598DE@smtp.pobox.com> (raw)
In-Reply-To: <795B0BF9C96CAB8918A75C8566FE4B63@smtp.pobox.com>
Using this flag helps when trying to combine commits. I noticed it in
the code for git/rebase when I was trying to figure out why my
invocation of git/rebase wasn't working. I still haven't figured it
out, but side-stepped the problem by doing mostly what git/rebase does
(create a temporary branch, apply patches, commit, then delete the
original branch and use the temporary branch to create a new branch
named after the original: clever).
Quoth Romano <unobe@cpan.org>:
> ---
> diff f48ee862768b677d0b0fca82a7efecd0b4fb3b06 a125c800817a8356de8580da78b7d9bd0ef95090
> --- a/sys/man/1/git
> +++ b/sys/man/1/git
> @@ -73,6 +73,9 @@
> .PP
> .B git/import
> [
> +.B -n
> +]
> +[
> .I commits...
> ]
> .PP
> @@ -432,7 +435,10 @@
> .PP
> .B Git/import
> imports a commit with message, author, and
> -date information.
> +date information. When passed the
> +.B -n
> +option, applies the contents of the commit without
> +committing to the branch.
>
> .PP
> .B Git/merge
>
>
prev parent reply other threads:[~2023-09-28 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 6:41 Romano
2023-09-28 7:10 ` unobe [this message]
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=096F8BC706832E96037C1D4F7E8598DE@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9front@9front.org \
/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).