Hi Cameron,
Glad to hear that the 'diff' approach was worth mentioning.
I'd agree that a --prefix option to checkout sounds sensible. The git
list is at Git List <g...@vger.kernel.org>. They only accept plain text
emails - any email containing HTML is classed as spam and deleted
without feedback. There are a number of git list archives. The current
leader is the 'public-inbox' https://public-inbox.org/git/?q= (check
the help)
You will also want to look at the new 'restore' command (coming soonish)
https://public-inbox.org/git/20190411131218.19195-1-pclo...@gmail.com/
The git list can feel intimidating, but that may depend on
sensibilities. They are usually very fair.
The Git code is mirrored on github https://github.com/git/git. For the
development code see gitster git://github.com/gitster/git.git.
The primary branches are: master (releasable), next (can be used), pu (
Potential Updates - all the half acceptable stuff, may include
breakages) and maint (maintenance, for fixes of older versions).
Philip
On 18/04/2019 12:55, Cameron Boehmer wrote:
Hey Philip,
Thanks for the context—and reminder that diff accepts a commit-ish ;)
I think that addresses the majority of the instances that I wanted
--prefix on checkout.
That said, there were a few times where I wanted to checkout an entire
subtree from another branch and do some less-than-straightforward
comingling of the two subtrees. In that case, I don't think diff would
be up to the task.
Not sure that this warrants a new feature, but (naively) it seems like
it'd be an easy one to add, and I'd be delighted to contribute. If I
wanted to offer, the devs mailling list would be the place to discuss?
Cameron
On Sun, Apr 14, 2019 at 9:07 PM Philip Oakley <philipoak...@iee.org
<mailto:philipoak...@iee.org>> wrote:
Hi Cameron,
Do you have a use case for this? I ask because the upstream folks
may be
expecting that the likes of `diff` would be the way to go for com
paring
what they would expect to be almost identical files...
As a side note the upstream git folks are looking at splitting the
'checkout' functionality (IIRC) between the treeish and the file-wise
things because the checkout command has become unwieldy (but it
won't be
going away..)
So it (--prefix) may be a valid use case suggestion for an easy
project
for the various folks who come along looking for projects
(Outreachy and
GSOC, etc.)
Have a look at the devs mailing list archive
https://public-inbox.org/git/?q=GSOC (adjust your search to taste)
Philip
On 14/04/2019 12:57, Cameron Boehmer wrote:
> I've found myself wanting to checkout paths from another branch w/o
> overwriting the same paths in my current branch. I was hoping to
find
> this functionality in `checkout`, but, alas, no `--prefix`
argument,
> like `checkout-index`'s, exists.
>
> I suppose I could do the standard checkout, move the checked-out
paths
> somewhere temporary, and then reset the paths in question, but I'd
> love to discover I don't have to write my own script to do this.
>
> Any ideas?
>
> Thanks,
> Cameron
> --
> You received this message because you are subscribed to the Google
> Groups "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from
it, send
> an email to git-users+unsubscr...@googlegroups.com
<mailto:git-users%2bunsubscr...@googlegroups.com>
> <mailto:git-users+unsubscr...@googlegroups.com
<mailto:git-users%2bunsubscr...@googlegroups.com>>.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
