From: Alejandro Colomar <alx@kernel.org>
To: Rik van Riel <riel@surriel.com>
Cc: linux-man@vger.kernel.org, kernel-team@meta.com,
linux-kernel@vger.kernel.org,
Matthew House <mattlloydhouse@gmail.com>,
Eric Biederman <ebiederm@xmission.com>
Subject: Using hg and git (Was: [PATCH v4] execve.2: execve also returns E2BIG if a string is too long)
Date: Wed, 11 Oct 2023 22:11:09 +0200 [thread overview]
Message-ID: <ZScBY7pn5x0xW2_h@debian> (raw)
In-Reply-To: <20231011125330.13dfe148@imladris.surriel.com>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Hi Rik,
On Wed, Oct 11, 2023 at 12:53:30PM -0400, Rik van Riel wrote:
> Sigh, once again I did a git commit --amend without the latest file change being
> included. The change below should be good. Working with both git and hg gets me sometimes :/
Been there. Hate that. I hope I don't touch hg(1) anymore. :D
Did you know about git-remote-hg(1)? It lets you work with hg remotes
without running hg(1) at all. It had some glitches from time to time
--TBH, I'm not sure if the glitches were from git-remote-hg(1), or just
that hg(1) is crap, or that the maintainers of the hg remote weren't so
good at it--, but nothing too irritating or destructive.
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-11 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 16:43 [PATCH v3] execve.2: execve also returns E2BIG if a string is too long Rik van Riel
2023-10-11 16:53 ` [PATCH v4] " Rik van Riel
2023-10-11 20:11 ` Alejandro Colomar [this message]
2023-10-11 20:14 ` Alejandro Colomar
2023-10-11 20:53 ` Rik van Riel
2023-10-11 23:45 ` Alejandro Colomar
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=ZScBY7pn5x0xW2_h@debian \
--to=alx@kernel.org \
--cc=ebiederm@xmission.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mattlloydhouse@gmail.com \
--cc=riel@surriel.com \
/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