From: Leila <muhtasib@gmail.com>
To: Michael Schubert <schu@schu.io>
Cc: git <git@vger.kernel.org>
Subject: Re: introduction
Date: Thu, 7 Jun 2012 00:00:44 -0400 [thread overview]
Message-ID: <CAA3EhHJaLuz05XJ51pbe=iHzPjg3vcgQAx9ceg00p+006yFQhg@mail.gmail.com> (raw)
In-Reply-To: <4FCDCB8B.4000103@schu.io>
On Tue, Jun 5, 2012 at 5:04 AM, Michael Schubert <schu@schu.io> wrote:
> On 06/04/2012 10:36 PM, Leila wrote:
>> 1) Commands are cryptic: I was thinking I could provide a wrapper to
>> simplify the commands, for example to undo a local commit, I can
>> introduce a "git undo commit", that wraps "reset" and will undo the
>> last commit. Or maybe "git rollback" is a better name?
>
> There's Legit [1], Easy Git [2] and probably more.
Ok fair.
>
>> 2) git undo command, that will undo the last command (if possible)?
>
> Not possible in general.
Undoing adds and commits? But I guess there isn't a long list here..
>> 3) Just like we have git-svn, maybe a svn-git?
>
> ?
>
>> Any help or if you can point me in the right direction, I'd appreciate
>> it. I can also start out by fixing some bugs to get into it. I
>> couldn't figure out how to see a list of bugs though.
>
> There's no bugtracker, just the ML.
Thanks!
> How to submit patches:
> https://raw.github.com/gitster/git/master/Documentation/SubmittingPatches
>
> You could check "old" GSoC Ideas:
> https://github.com/peff/git/wiki/SoC-2012-Ideas
Thanks I've reached out to Peff and Thomas.
>> How does one contribute to your documentation? Would it be submitting
>> a patch just like with code?
>
> Yes.
>
> HTH.
>
> [1] http://www.git-legit.org
> [2] http://people.gnome.org/~newren/eg/
>
next prev parent reply other threads:[~2012-06-07 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA3EhHJCRF05Q0xzzOWupVMjmKPbWAq1KNcU9Mmp8g1iH2B0zA@mail.gmail.com>
2012-06-04 20:36 ` introduction Leila
2012-06-05 9:04 ` introduction Michael Schubert
2012-06-07 4:00 ` Leila [this message]
2012-06-05 9:40 ` introduction Andreas Ericsson
2012-06-07 4:03 ` introduction Leila
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA3EhHJaLuz05XJ51pbe=iHzPjg3vcgQAx9ceg00p+006yFQhg@mail.gmail.com' \
--to=muhtasib@gmail.com \
--cc=git@vger.kernel.org \
--cc=schu@schu.io \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).