All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] problem with sudo patch file name
Date: Mon, 10 Sep 2012 08:35:24 +0200	[thread overview]
Message-ID: <87har61j2r.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CANxTyt5k19J-iyEXg4FZfmtNZVJL+qnCKYUo9PSeGf=D5C6NJw@mail.gmail.com> (Danomi Manchego's message of "Fri, 7 Sep 2012 22:01:23 -0400")

>>>>> "Danomi" == Danomi Manchego <danomimanchego123@gmail.com> writes:

 Danomi> Hi,
 Danomi> I recently started to update our project to buildroot-2012.08. ?When I went to
 Danomi> check into source control, I got an error from this file:

 Danomi> ? ? package/sudo/
 Danomi> sudo-1.8.5p2-backport-commit-8209:0c4e3f68b2f5-from-upstream.patch

 Danomi> The problem is the colon (":") in the file name. ?I think the
 Danomi> problem is that our source control system is on a Windows
 Danomi> server

 Danomi> Would there be interest in a patch that renames this file to
 Danomi> remove the colon?  ?We could change the colon to an underscore
 Danomi> or dash, but I see that the upstream commit number is in a
 Danomi> comment at the top of the patch, so I don't know that naming
 Danomi> the file after the upstream commit number is actually helpful.
 Danomi> ?Maybe "sudo-1.8.5p2-backport-cross-compile-fix.patch" would be
 Danomi> better?

Thanks for the heads up. Instead of renaming the file I bumped the sudo
package to the recent 1.8.6 release (so we don't need the patch any
more), but I'll try to remember for the future.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2012-09-10  6:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08  2:01 [Buildroot] problem with sudo patch file name Danomi Manchego
2012-09-08  3:29 ` W.P.
2012-09-10  6:35 ` Peter Korsgaard [this message]

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=87har61j2r.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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.