From: Christian Couder <chriscool@tuxfamily.org>
To: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>, Petr Baudis <pasky@ucw.cz>,
git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCHv5 GSoC] gitweb: Move static files into seperate subdirectory
Date: Tue, 25 May 2010 08:32:58 +0200 [thread overview]
Message-ID: <201005250832.58350.chriscool@tuxfamily.org> (raw)
In-Reply-To: <AANLkTikOMuugbWqnbkUYwPsxq6z9Eo3E3MrX1jIE5juS@mail.gmail.com>
On Tuesday 25 May 2010 06:51:18 Pavan Kumar Sunkara wrote:
> On Tue, May 25, 2010 at 9:54 AM, Christian Couder
>
> <chriscool@tuxfamily.org> wrote:
> > On Tuesday 25 May 2010 06:30:49 Pavan Kumar Sunkara wrote:
> >> It's not a problem with the version, it's a problem with your system.
> >> echo -e didn't create a binary as expected. You can tell it by seeing
> >> this line:
> >>
> >> bar => sub/bar | 0
> >>
> >> rather than this
> >>
> >> bar => sub/bar | Bin 5 -> 5 Bytes
> >>
> >> Change your script to copy a binary file into bar instead of using
> >> 'echo -e 'bar\()' and you will see the difference.
> >
> > Yeah I changed "#!/bin/sh" to "#!/bin/bash" and it does not work now.
> > It's a problem because /bin/sh is dash on kubuntu.
> >
> > Thanks,
> > Christian.
>
> Manually adding the diff lines for both the binary files and applying
> that patch worked for me.
> So, shall I send it to git list for now ?
Yes please!
Thanks,
Christian.
next prev parent reply other threads:[~2010-05-25 7:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 15:22 [PATCHv5 GSoC] gitweb: Move static files into seperate subdirectory Pavan Kumar Sunkara
2010-05-24 20:05 ` Christian Couder
2010-05-24 20:28 ` Pavan Kumar Sunkara
2010-05-25 0:37 ` Jakub Narebski
2010-05-25 3:14 ` Christian Couder
2010-05-25 4:30 ` Pavan Kumar Sunkara
2010-05-25 4:24 ` Christian Couder
2010-05-25 4:51 ` Pavan Kumar Sunkara
2010-05-25 6:32 ` Christian Couder [this message]
2010-05-25 21:22 ` Christian Couder
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=201005250832.58350.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=normalperson@yhbt.net \
--cc=pasky@ucw.cz \
--cc=pavan.sss1991@gmail.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 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).