From: Jon Loeliger <jdl@freescale.com>
To: git@vger.kernel.org
Subject: git-pull.sh's bad mode
Date: Tue, 08 Nov 2005 08:19:38 -0600 [thread overview]
Message-ID: <E1EZUK2-0005EG-56@jdl.com> (raw)
In-Reply-To: 81b0412b0511080023k1384dc26j944e9a07987be436@mail.gmail.com
Public apology and brown paper bag. My patch
accidentally twiddled the mode on git-pull.sh:
Signed-off-by: Jon Loeliger <jdl@freescale.com>
---
Documentation/git-pull.txt | 17 +++++++----------
Documentation/merge-options.txt | 16 ++++++++++++++++
Documentation/merge-pull-opts.txt | 14 --------------
git-format-patch.sh | 4 ++++
git-pull.sh | 12 +++++++++++-
9 files changed, 70 insertions(+), 48 deletions(-)
create mode 100644 Documentation/fetch-options.txt
create mode 100644 Documentation/merge-options.txt
delete mode 100644 Documentation/merge-pull-opts.txt
mode change 100755 => 100644 git-pull.sh
next reply other threads:[~2005-11-08 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 14:19 Jon Loeliger [this message]
2005-11-08 16:25 ` git-pull.sh's bad mode Junio C Hamano
2005-11-08 16:35 ` Petr Baudis
2005-11-08 19:30 ` Junio C Hamano
2005-11-08 19:39 ` Petr Baudis
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=E1EZUK2-0005EG-56@jdl.com \
--to=jdl@freescale.com \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).