From: Devin Lehmacher <lehmacdj@gmail.com>
To: git@vger.kernel.org
Subject: [GSoC] Proposal Discussion
Date: Mon, 27 Mar 2017 18:17:08 -0400 [thread overview]
Message-ID: <20170327221707.GA34039@mango1> (raw)
Hello everyone,
I am a student studying Computer Science at Cornell University. I
already completed a microproject, Move ~/.git-credential-cache/socket to
$XDG_CACHE_HOME/credential/socket a week and a half ago or so.
I am interested in 2 different projects and would like some advice on
them, to help me decide which one to submit a proposal for.
1. `git rebase -i` conversion.
I was initially the most interested in this project but realize that
after having a very busy week last week that Ivan Tham started
[discussion][1] about this project. Would it be appropriate to submit
a proposal for a project that someone else also wants to work on?
2. formatting tool improvements.
There are four different git commands mentioned [here][2] as possible
tools to improve as can be seen in the email. Of those I think it
would make the most sense to extend `git name-rev`. It seems best
suited to the desired behavior. It would need to be extended to
understand rev's that refer to objects rather than just a commit-ish
and also add formatting support similar to the information that log
and for-each-ref can output. Since this doesn't seem like much work,
would it be feasible to generalize and somewhat standardize all of
the formatting commands?
[1]: https://public-inbox.org/git/20170320164154.xBcU6rG0C%25pickfire@riseup.net/
[2]: https://public-inbox.org/git/CA+P7+xr4ZNCCJkS0=yR-FNu+MrL60YX-+Wsz9L_5LCNhnY_d=A@mail.gmail.com/
Thanks for any feedback you may have,
Devin
next reply other threads:[~2017-03-27 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 22:17 Devin Lehmacher [this message]
2017-03-28 5:52 ` [GSoC] Proposal Discussion Christian Couder
2017-03-28 15:49 ` Devin Lehmacher
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=20170327221707.GA34039@mango1 \
--to=lehmacdj@gmail.com \
--cc=git@vger.kernel.org \
/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.