* [Buildroot] problem with sudo patch file name
@ 2012-09-08 2:01 Danomi Manchego
2012-09-08 3:29 ` W.P.
2012-09-10 6:35 ` Peter Korsgaard
0 siblings, 2 replies; 3+ messages in thread
From: Danomi Manchego @ 2012-09-08 2:01 UTC (permalink / raw)
To: buildroot
Hi,
I recently started to update our project to buildroot-2012.08. When I went
to check into source control, I got an error from this file:
package/sudo/sudo-1.8.5p2-backport-commit-8209:0c4e3f68b2f5-from-upstream.patch
The problem is the colon (":") in the file name. I think the problem is
that our source control system is on a Windows server
Would there be interest in a patch that renames this file to remove the
colon? We could change the colon to an underscore or dash, but I see that
the upstream commit number is in a comment at the top of the patch, so I
don't know that naming the file after the upstream commit number is
actually helpful. Maybe "sudo-1.8.5p2-backport-cross-compile-fix.patch"
would be better?
Danomi -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120907/6a819d40/attachment.html>
^ permalink raw reply [flat|nested] 3+ messages in thread* [Buildroot] problem with sudo patch file name
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
1 sibling, 0 replies; 3+ messages in thread
From: W.P. @ 2012-09-08 3:29 UTC (permalink / raw)
To: buildroot
U?ytkownik Danomi Manchego napisa?:
> Hi,
>
> I recently started to update our project to buildroot-2012.08. When I went
> to check into source control, I got an error from this file:
>
>
> package/sudo/sudo-1.8.5p2-backport-commit-8209:0c4e3f68b2f5-from-upstream.patch
>
> The problem is the colon (":") in the file name. I think the problem is
> that our source control system is on a Windows server
>
>> that our source control system is on a Windows server
As I read on the net, even M$ DON'T do that...
[from the -10 years past: "M$ MAKES its $$ on Windows, but COUNTS it on
AS/400..." - now IBM pSeries - or something..,
THEY DON'T rely on their own products... who wants "better" recommendation?]
W.P.
^ permalink raw reply [flat|nested] 3+ messages in thread* [Buildroot] problem with sudo patch file name
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
1 sibling, 0 replies; 3+ messages in thread
From: Peter Korsgaard @ 2012-09-10 6:35 UTC (permalink / raw)
To: buildroot
>>>>> "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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-09-10 6:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox