Re: [PATCH 0/3] Fixing volatile HEAD in push.default = current

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH 0/3] Fixing volatile HEAD in push.default = current

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:57:25

Andreas Krey [off-list ref] writes:
On Thu, 23 May 2013 13:25:55 +0000, Ramkumar Ramachandra wrote:
quoted
Junio C Hamano wrote:
quoted
    I have "largedir" I want to get rid of, but there is a directory
    I want to save, "largedir/precious", in it, so I do

        cp -R largedir/precious precious

    and then run 'rm -rf largedir' in another terminal in parallel.
'mv largedir/precious precious; rm -rf largedir'? No race here.
Yeah, but 'cp -R largedir/precious precious; rm -fr largedir' is the
same thing.  Ram's original issue was "I do something else in
another terminal without waiting for the first command to finish".

Even with 'mv', between the time the main in mv starts and the
process finally issues rename(2) on the directory, you can start
running what competes and interferes with it in another terminal,
so it does not fundamentally change anything, I would have to say.

Re: [PATCH 0/3] Fixing volatile HEAD in push.default = current

From: Andreas Krey <hidden>
Date: 2016-06-15 22:57:25

On Thu, 23 May 2013 07:45:34 +0000, Junio C Hamano wrote:
...
Even with 'mv', between the time the main in mv starts and the
process finally issues rename(2) on the directory, you can start
running what competes and interferes with it in another terminal,
so it does not fundamentally change anything, I would have to say.
Not fundamentally, it's just that the mv is fast enough you wouldn't
even think of switch to another term/backgrounding it.

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help