AIN MEDICARE is searching for reliable COMPANIES/PERSONS to represent its
interests in your jurisdiction. Please advice if you are interested in working
with us.
Dr Syed Ibrahim Ismail
Director
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
On Sun, Oct 6, 2013 at 4:27 PM, Stefan Beller
stefanbel...@googlemail.com wrote:
@@ -688,7 +688,7 @@ static void write_refspec_config(const char*
src_ref_prefix,
if (option_mirror || !option_bare) {
if (option_single_branch !option_mirror) {
-
On Sun, Oct 06, 2013 at 09:48:29PM +0100, Ramsay Jones wrote:
Sparse issues an 'git_parse_unsigned' was not declared. Should it
be static? warning. In order to suppress this warning, since this
symbol only requires file scope, we simply add the static modifier
to its declaration.
Thanks.
On Sun, Oct 06, 2013 at 05:50:00PM +, brian m. carlson wrote:
On Sun, Oct 06, 2013 at 05:38:24PM +0200, Daniel Stenberg wrote:
On Sun, 6 Oct 2013, brian m. carlson wrote:
If there's a way to make Apache with mod_auth_kerb do that with
curl, then it doesn't require a change to git,
On Mon, Oct 07, 2013 at 07:24:11AM -0400, Jeff King wrote:
However, one thing I expected to work but didn't is:
echo '*' .gitignore
echo '!*' my_dir/.gitignore
That _does_ work for attributes, like:
echo '* foo=one' .gitattributes
echo '* foo=two' my_dir/.gitattributes
where
Currently git cherry determines whether a commit has been merged
upstream by calculating its patch-id and looking for that in the
upstream branch. Is there any reason why it couldn't also look for
(cherry picked from commit ...) lines which are automatically added
by cherry-pick's -x switch?
On Mon, Oct 07, 2013 at 09:16:17PM +0100, Adam Spiers wrote:
Currently git cherry determines whether a commit has been merged
upstream by calculating its patch-id and looking for that in the
upstream branch. Is there any reason why it couldn't also look for
(cherry picked from commit ...)
On Mon, Oct 07, 2013 at 08:02:41AM -0400, Jeff King wrote:
Yeah, instead we try to make two separate requests, and assume that the
first one clears the path for any further requests. Of course that
doesn't work for auth methods that actually negotiate for each request.
We should probably
8 matches
Mail list logo
