]> git.madduck.net Git - code/vcsh.git/commit

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

projects / code / vcsh.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d018850) | patch
Rename `foo` to a meaningful name `repo_name`
authorYuval Langer <yuval.langer@gmail.com>
Sun, 7 Sep 2014 14:39:22 +0000 (17:39 +0300)
committerYuval Langer <yuval.langer@gmail.com>
Mon, 8 Sep 2014 20:28:49 +0000 (23:28 +0300)
commit0bd39b20cea2833de45482e077917947c0b99d61
tree059e3e51cca5da0153f8a40f5c4ccd4b04f0272ctree | snapshot
parentd01885099326c1b630753608eda60ed201375d9dcommit | diff
Rename `foo` to a meaningful name `repo_name`

I get lost within all of those meaningless names.
It is useful to give things meaningful names, especially in documentation.
doc/README.md diff | blob | history
version controlled RC files

Legalese

All content available in this repository is copyright © martin f. krafft, unless otherwise noted.

All files and their content are released under the terms of the Artistic Licence 2.0, unless otherwise noted.

The operator of this repository shall not be held liable for offending content in pages linking to or linked from these page, nor does he endorse their content unless stated otherwise.