From: Michael Schubert <schu@schu.io>
To: Leila <muhtasib@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: introduction
Date: Tue, 05 Jun 2012 11:04:11 +0200 [thread overview]
Message-ID: <4FCDCB8B.4000103@schu.io> (raw)
In-Reply-To: <CAA3EhH+P_JeVGhRmL-kHOc0cTCiGQmv505XjgAv0kT1PAfjTyw@mail.gmail.com>
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.
> 2) git undo command, that will undo the last command (if possible)?
Not possible in general.
> 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.
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
> 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-05 9:12 UTC|newest]
Thread overview: 23+ 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 ` Michael Schubert [this message]
2012-06-07 4:00 ` introduction Leila
2012-06-05 9:40 ` introduction Andreas Ericsson
2012-06-07 4:03 ` introduction Leila
2025-07-10 10:49 Introduction Samiksha Palav
-- strict thread matches above, loose matches on Subject: below --
2025-07-10 10:49 Introduction Samiksha Palav
2025-07-10 10:43 Introduction Samiksha Palav
2025-03-18 16:10 introduction erick karanja
2013-09-25 15:10 Introduction Ho Wan Chan
2013-03-12 1:02 Introduction Chia-Juch Chang
2011-02-05 21:06 Introduction Ian Porter
2011-02-05 21:24 ` Introduction Srdjan Todorovic
2003-09-10 4:22 Introduction Muthukumar
2003-09-10 5:11 ` Introduction Davide Libenzi
2003-09-10 4:22 Introduction Muthukumar
2002-06-19 21:32 introduction Sam Halliday
2002-06-19 21:44 ` introduction John Levon
2001-06-25 6:54 KSEG2 Segment not used on Linux? Ralf Baechle
2001-06-25 14:53 ` introduction Timothy Daly
2001-06-26 1:53 ` introduction George Gensure
2001-06-26 1:53 ` introduction George Gensure
2001-03-02 2:11 Introduction J. Hart
1999-09-03 17:52 Introduction Walter Keeler
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=4FCDCB8B.4000103@schu.io \
--to=schu@schu.io \
--cc=git@vger.kernel.org \
--cc=muhtasib@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 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.