From: COGONI Guillaume <cogoni.guillaume@gmail.com>
To: git@vger.kernel.org
Cc: Matthieu.Moy@univ-lyon1.fr, git.jonathan.bressat@gmail.com,
derrickstolee@github.com, guillaume.cogoni@gmail.com
Subject: [PATCH 0/1] documentation: guide of best practices for GIT developer
Date: Tue, 12 Apr 2022 22:25:56 +0200 [thread overview]
Message-ID: <20220412202557.32101-1-cogoni.guillaume@gmail.com> (raw)
Hello,
This patch has for purpose to introduce a file where GIT developers can share
their own best practices, tools or workflows to the community in order to
help the GIT developer.
The discussion about this idea begin in this thread:
Message-Id: <20220407204001.112287-2-cogoni.guillaume@gmail.com>
Derrick Stolee and I agreed that is can be a good idea.
And, I think, it can help a newcomer, but not necessarily people with a
lot of experience on various projects. But, we can give it a try and
see where it goes.
PS:
I do not believe it is a good idea to give detailed tutorials because there
are a lot on the internet. However, give the reader pros, cons and curiosity
to test those tools, practice or workflow can be really good.
It's better if the tools are open source and free, but it is not mandatory.
Sincerly,
Cogoni Guillaume
COGONI Guillaume (1):
documentation: guide of best practices for GIT developer
Documentation/Makefile | 1 +
Documentation/WorkingOnGit.txt | 53 ++++++++++++++++++++++++++++++++++
2 files changed, 54 insertions(+)
create mode 100644 Documentation/WorkingOnGit.txt
base-commit: ab1f2765f78e75ee51dface57e1071b3b7f42b09
--
2.25.1
next reply other threads:[~2022-04-12 23:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 20:25 COGONI Guillaume [this message]
2022-04-12 20:25 ` [PATCH 1/1] documentation: guide of best practices for GIT developer COGONI Guillaume
2022-04-13 14:36 ` [PATCH 0/1] " Shaoxuan Yuan
2022-04-13 16:36 ` Guillaume Cogoni
2022-04-16 12:34 ` [PATCH v1 0/1] Documentation/ToolsOnGit.txt: gather information about tools COGONI Guillaume
2022-04-16 12:34 ` [PATCH v1 1/1] " COGONI Guillaume
[not found] ` <63d7dc69656e47f7bc7bce4839711f32@SAMBXP02.univ-lyon1.fr>
2022-04-16 13:25 ` Matthieu Moy
2022-04-16 14:51 ` Philip Oakley
2022-04-16 17:11 ` Junio C Hamano
2022-04-17 9:35 ` [PATCH v2 0/1] Documentation/ToolsForGit.txt: Tools for developing Git COGONI Guillaume
2022-04-17 9:35 ` [PATCH v2 1/1] " COGONI Guillaume
[not found] ` <33d2087c66e44037b03db818dae60fea@SAMBXP02.univ-lyon1.fr>
2022-04-17 12:25 ` [PATCH v2 0/1] " Matthieu Moy
2022-04-20 13:06 ` [PATCH v3 " COGONI Guillaume
2022-04-20 13:06 ` [PATCH v3 1/1] " COGONI Guillaume
2022-04-20 21:23 ` Junio C Hamano
2022-04-21 8:45 ` [PATCH v4 0/1] " COGONI Guillaume
2022-04-21 8:45 ` [PATCH v4 1/1] " COGONI Guillaume
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=20220412202557.32101-1-cogoni.guillaume@gmail.com \
--to=cogoni.guillaume@gmail.com \
--cc=Matthieu.Moy@univ-lyon1.fr \
--cc=derrickstolee@github.com \
--cc=git.jonathan.bressat@gmail.com \
--cc=git@vger.kernel.org \
--cc=guillaume.cogoni@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).