git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Prudhvee Narasimha Sadha <prudhvi.sada@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git Newbie - GSoC mini Project
Date: Wed, 04 Mar 2015 08:49:46 +0100	[thread overview]
Message-ID: <1425455386.1193.17.camel@kaarsemaker.net> (raw)
In-Reply-To: <CAMS+ib3LRT0xSzW-8Qkubbxc22RSifq=V8Za6TCrbDi2ko2ekA@mail.gmail.com>

On wo, 2015-03-04 at 11:50 +0530, Prudhvee Narasimha Sadha wrote:
>        I'm a newbie to git. I started  working on git. I cloned the
> git repository and started hacking it. I need a suggestion on how to
> start working on the micro project "
> 
> Make "git -C '' cmd" not to barf".

git -C '' cmd currently throws an error:

$ git -C '' status
fatal: Cannot change to '': No such file or directory

So the two things you should do are

- Determine what the desired behavior would be
- Implementing that behavior

For the first step, I'd send a mail to this list asking people for
input, paying special attention to the responses of the core maintainers
and possible GSOC mentors (I'm not one of them, but I think the error is
actually the right behavior, I'd prefer git -C "$repodir" to bomb out if
$repodir is unset. On the other hand cd '' is equivalent to not cd'ing
at all so there's precedent to change this).

For the second step, you'll need to find the bit of code where the -C
option is handled and add a special case for the empty string to do what
came out of the discussion about wanted behavior.

-- 
Dennis Kaarsemaker
www.kaarsemaker.net

  reply	other threads:[~2015-03-04  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  6:20 Git Newbie - GSoC mini Project Prudhvee Narasimha Sadha
2015-03-04  7:49 ` Dennis Kaarsemaker [this message]
2015-03-04  7:58   ` Matthieu Moy

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=1425455386.1193.17.camel@kaarsemaker.net \
    --to=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    --cc=prudhvi.sada@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).