From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Ryan Anderson <ryan@michonline.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Applying a graft to a tree and "rippling" the changes through the history
Date: 06 Nov 2005 14:43:17 -0800 [thread overview]
Message-ID: <867jblpfcq.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <436E85DA.1080904@michonline.com>
>>>>> "Ryan" == Ryan Anderson <ryan@michonline.com> writes:
Ryan> chdir($ARGV[0]);
That's dangerous without an "or-die". Being in the wrong directory
before you do a lot of edits is a good way to bust your disk. :)
Ryan> my ($commit,@parents) = split /\s+/;
split with no args splits $_ on whitespace, tossing leading whitespace,
just in case they ever put whitespace indentation ahead.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-11-06 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 22:38 [RFC] Applying a graft to a tree and "rippling" the changes through the history Ryan Anderson
2005-11-06 22:43 ` Randal L. Schwartz [this message]
2005-11-07 1:45 ` Junio C Hamano
2005-11-07 2:22 ` Ryan Anderson
2005-11-18 8:49 ` Matthias Urlichs
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=867jblpfcq.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=ryan@michonline.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.