"Robert P. J. Day" writes:
> ... so if, in the kernel source
> tree, i ran:
>
> $ git rm \*.c
>
> i would end up removing *all* 25,569 "*.c" files in the kernel source
> repository.
Yes, as that is exactly what the command line asks Git to do.
If you said
$ git rm *.c
then the shell exp
Jeff King writes:
> On Sat, Oct 07, 2017 at 03:12:08PM -0400, Derrick Stolee wrote:
>
>> In my local copy, I added a test to p4211-line-log.sh that runs "git log
>> --raw -r" and tested it on three copies of the Linux repo. In order, they
>> have 1 packfile (0 loose), 24 packfiles (0 loose), and
On Sat, 2017-10-07 at 15:43 -0400, Robert P. J. Day wrote:
> it's been a long week, so take this in the spirit in which it is
> intended ... i think the "git rm" command and its man page should be
> printed out, run through a paper shredder, then set on fire. i can't
> remember the last time i sa
On Sat, 7 Oct 2017, Paul Smith wrote:
> On Sat, 2017-10-07 at 15:43 -0400, Robert P. J. Day wrote:
> > it's been a long week, so take this in the spirit in which it is
> > intended ... i think the "git rm" command and its man page should be
> > printed out, run through a paper shredder, then set
On Sat, 7 Oct 2017, Theodore Ts'o wrote:
> On Sat, Oct 07, 2017 at 03:43:43PM -0400, Robert P. J. Day wrote:
> > > -r
> > > Recursively remove the contents of any directories that match
> > > ``.
> > >
> > > or something.
> >
> > it's been a long week, so take this in the spirit in which i
On Fri, Oct 06, 2017 at 01:39:16PM -0400, Robert P. J. Day wrote:
> On Fri, 6 Oct 2017, Junio C Hamano wrote:
> > This is primarily why .git/info/exclude exists. A user who does not
> > use the same set of tools to work on different projects may not be
> > able to use ~/.gitconfig with core.exclud
On Sat, Oct 07, 2017 at 03:43:43PM -0400, Robert P. J. Day wrote:
> > -r
> > Recursively remove the contents of any directories that match
> > ``.
> >
> > or something.
>
> it's been a long week, so take this in the spirit in which it is
> intended ... i think the "git rm" command and
On Sat, 7 Oct 2017, Jeff King wrote:
> On Sat, Oct 07, 2017 at 03:32:24PM -0400, Robert P. J. Day wrote:
>
> > > Nothing, because there is nothing to recurse in the pathspecs you've
> > > given.
> > >
> > > Try:
> > >
> > > $ git rm drivers
> > > fatal: not removing 'drivers' recursively witho
On Sat, Oct 07, 2017 at 03:32:24PM -0400, Robert P. J. Day wrote:
> > Nothing, because there is nothing to recurse in the pathspecs you've
> > given.
> >
> > Try:
> >
> > $ git rm drivers
> > fatal: not removing 'drivers' recursively without -r
> >
> > versus
> >
> > $ git rm -r drivers
> >
On Sat, Oct 07, 2017 at 03:12:08PM -0400, Derrick Stolee wrote:
> In my local copy, I added a test to p4211-line-log.sh that runs "git log
> --raw -r" and tested it on three copies of the Linux repo. In order, they
> have 1 packfile (0 loose), 24 packfiles (0 loose), and 23 packfiles
> (~324,000 l
On Sat, 7 Oct 2017, Jeff King wrote:
> On Sat, Oct 07, 2017 at 03:12:01PM -0400, Robert P. J. Day wrote:
>
> > ok, in that case, can you give me an example where "-r" makes a
> > difference, given that the man page refers to "a leading directory
> > name being given"? let's use as an example the
On Sat, Oct 07, 2017 at 03:12:01PM -0400, Robert P. J. Day wrote:
> ok, in that case, can you give me an example where "-r" makes a
> difference, given that the man page refers to "a leading directory
> name being given"? let's use as an example the linux kernel source,
> where there are a *ton*
On 10/6/2017 10:11 AM, Jeff King wrote:
On Thu, Oct 05, 2017 at 08:39:42AM -0400, Derrick Stolee wrote:
I'll run some perf numbers for these commands you recommend, and also see if
I can replicate some of the pain points that triggered this change using the
Linux repo.
Thanks!
-Peff
In my
On Sat, 7 Oct 2017, Todd Zullinger wrote:
> Robert P. J. Day wrote:
> >
> > was just testing variations of "git rm", and man page claims:
> >
> > -r Allow recursive removal when a leading directory name is given.
> >
> > i tested this on the "pro git" book repo, which contains a top-level "b
Robert P. J. Day wrote:
was just testing variations of "git rm", and man page claims:
-r
Allow recursive removal when a leading directory name is given.
i tested this on the "pro git" book repo, which contains a top-level
"book/" directory, and quite a number of "*.asc" files in vario
was just testing variations of "git rm", and man page claims:
-r
Allow recursive removal when a leading directory name is given.
i tested this on the "pro git" book repo, which contains a top-level
"book/" directory, and quite a number of "*.asc" files in various
subdirectories one or m
--
Greetings
my name is miss myriam
No Matter the Good and bad that we face
Everyday in our life there is still a Space of love in our Heart.
and i count it a Great Privileged in Communicating with someone who
will Truly be honest with me
i need you as a business partner or a
friend who will help
--
Dear Friend,
Good day. I am Mr. Abel Kaba. I am working with one of the prime banks
in Burkina Faso. I have decided to contact you for a financial
transaction which values $14,500,000.00 (Fourteen Million Five Hundred
Thousand USA Dollars). This is an abandoned fund that belongs to a
late fore
Phillip Wood writes:
> From: Phillip Wood
>
> Signed-off-by: Phillip Wood
> ---
This seems to do a lot more than just moving code, most notably, it
uses setenv() to affect what happens in any subprocesses we may
spawn, and it is unclear if it was verified that this patch is free
of unwanted co
On Sat, Oct 7, 2017 at 4:51 AM, Junio C Hamano wrote:
> FWIW, the previous one is at
> https://public-inbox.org/git/20170929094453.4499-1-pc44...@gmail.com
> Hope that helps ;-)
Thanks, it does help.
Having scanned discussions of previous versions, I see that some of my
comments do indeed ov
Prathamesh Chavan writes:
> Changes in v7:
FWIW, the previous one is at
https://public-inbox.org/git/20170929094453.4499-1-pc44...@gmail.com
Alternatively, the References link can be followed back from the
cover letter to go back to quite an early iteration of the series.
Hope that helps
21 matches
Mail list logo