From: Todd Zullinger <tmz@pobox.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Junio C Hamano <gitster@pobox.com>,
Edward Thomson <ethomson@edwardthomson.com>,
git@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] recover: restoration of deleted worktree files
Date: Sat, 4 Aug 2018 13:33:40 -0400 [thread overview]
Message-ID: <20180804173340.GK3764@zaya.teonanacatl.net> (raw)
In-Reply-To: <alpine.LFD.2.21.1808041214550.28242@localhost.localdomain>
Hi,
Robert P. J. Day wrote:
> On Sat, 4 Aug 2018, Junio C Hamano wrote:
>> In other words, I think this patch can be a fine addition to
>> somebody else's project (i.e. random collection of scripts that may
>> help Git users), so let's see how I can offer comments/inputs to
>> help you improve it. So I won't comment on lang, log message, or
>> shell scripting style---these are project convention and the
>> git-core convention won't be relevant to this patch.
>
> not sure how relevant this is, but fedora bundles a bunch of neat
> utilities into two packages: git-tools and git-extras. i have no idea
> what relationship those packages have to official git, or who decides
> what goes into them.
For anyone curious, those packages (git-extras and
git-tools) are both entirely separate projects upstream and
in the fedora packaging. A git-recover script may well be a
good fit in one of those upstream projects.
The git-(extras|tools) package names are a bit confusing
IMO. But it's probably more confusing that they each add a
number of git-* commands in the default PATH the way they're
packaged.
We do package some bits from contrib/ (e.g. completion,
subtree, etc.) in the fedora git packages. We don't add
scripts and commands from outside of the git tarballs as
part of the fedora git package, though.
So far, I don't recall anyone filing a bug report about
commands from git-extras or git-tools against git. So it
seems that users of those additional packages aren't being
confused, thankfully.
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Between two evils, I always pick the one I never tried before.
-- Mae West
next prev parent reply other threads:[~2018-08-04 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 14:22 [RFC PATCH 0/1] Introduce git-recover Edward Thomson
2018-08-04 14:24 ` [RFC PATCH 1/1] recover: restoration of deleted worktree files Edward Thomson
2018-08-04 15:54 ` Junio C Hamano
2018-08-04 16:17 ` Robert P. J. Day
2018-08-04 17:33 ` Todd Zullinger [this message]
2018-08-04 16:19 ` Edward Thomson
2018-08-04 16:48 ` Junio C Hamano
2018-08-05 1:34 ` [RFC PATCH 0/1] Introduce git-recover Jonathan Nieder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180804173340.GK3764@zaya.teonanacatl.net \
--to=tmz@pobox.com \
--cc=ethomson@edwardthomson.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rpjday@crashcourse.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).