git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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/

  reply	other threads:[~2012-06-05  9:12 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   ` 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

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=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.
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).