Re: [git-users] Feature request: -np (shorthand for --no-pager)

[Philip Oakley]

- Original Message - 
  From: Ashley Coolman 
  To: Git for human beings 
  Sent: Thursday, April 28, 2016 8:59 AM
  Subject: [git-users] Feature request: -np (shorthand for --no-pager)


  Would make sense, no?
As others have said, the single dash allows multiple single character options 
to be concatenated. the double-dash is used for options that take more than one 
character.

However you may be in luck with the ability to shorten long options to the 
minimum number of characters that makes the option unique. Try "--no-p", or 
"--no-pa", etc.  (this may depend on the comand that you apply it to...)

Philip

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] I am a newbie

[Konstantin Khomoutov]

On Thu, 28 Apr 2016 13:43:51 -0700 (PDT)
Alekhya Vellanki  wrote:

> I'd like to start contributing to git.
> 
> I have absolutely no idea about open source projects contributions.
> I am also pretty unclear about what bugs,patches etc are.
> When I tried reading source codes of a few project ideas for GSoc
> 2016, I could hardly understand anything.
> 
> I am good with C, C++.I am currently learning JAVA, python and shell 
> scripting.

I'm a bit uncomfortable to say this, but writing "I am good with C,
C++" right next to "I am also pretty unclear about what bugs,patches
etc are." and "...could hardly understand anything" is really a bold
statement: by the time someone declares they are good at C, they surely
are good at bugs, patches and software in general.

> How do I start off with open source project contributions?I want to
> be a part of GSoC 2017(Atleast submit a decent project proposal ;P).

Again, I'd really not want to sound blunt but it appears you merely
intend to somehow kickstart your career by forming up a competitive
portfolio (like "I was participating in GSoC" blah blah).
Not bad in itself but really this is a two-sided coin: the purpose of
GSoC is not merely get students involved but get the useful things
implemented in a participating software project, and that means the
students should have the skills on par with the task at hand.

> Please guide me right from the scratch.

Please read [1] for an answer to a similar request.

For now, your best tactic -- beyond learning and playing with writing
simple software -- should be the so-called "lurking".  Lurking means
quietly *watching* how the hard-core developers work on a software
project: how they discuss bugs and patches and proposed features;
studying commits they made in their project's repository.

What you did is suddenly having appeared out of thin air, evidently
with no prior familiarity with even the basics of software development
and asking to make you working on a really complicated piece of
software.  You definitely should work up your craftmanship on more
simple project (even on toy projects for the first time).

You could start reading through [2] which is intended to serve as a
gentle introduction to F/OSS development and the tooling it uses
(bugreports and patches included).

I with you good luck with learning!  Please not be put off by my rather
direct but honest and warm-hearted debunk. ;-)

1. https://groups.google.com/d/msg/git-users/QIGR_EBiPMM/YjAvrvd_AgAJ
2. http://yakking.branchable.com/

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] I am a newbie

[Alekhya Vellanki]

Hi everybody,

I'd like to start contributing to git.

I have absolutely no idea about open source projects contributions.
I am also pretty unclear about what bugs,patches etc are.
When I tried reading source codes of a few project ideas for GSoc 2016, I 
could hardly understand anything.

I am good with C, C++.I am currently learning JAVA, python and shell 
scripting.

How do I start off with open source project contributions?I want to be a 
part of GSoC 2017(Atleast submit a decent project proposal ;P).

Please guide me right from the scratch.

Thanks in advance.
-Alekhya

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Feature request: -np (shorthand for --no-pager)

[Dale R. Worley]

Ashley Coolman  writes:
> Would make sense, no?

Unfortunately, no.  The convention is that "--" is used to start long
options, which may have an optional value which is started with "=":

--[a-zA-Z0-0]+(=.*)?

Options that start with "-" use the long-established conventions for
single-letter options:  Each letter after the "-" is interpreted in turn
as an option name.  However, if an option is one that takes a value,
then the remainder of the argument is the option's value, or if there
are no further characters in the argument, the entire next argument is
the option's value.  Thus, "-np" means the same thing as "-n -p", while
"--np" specifies a single option.

The degree to which various packages follow these rules varies, but
they're generallly observed.  The Gnu utilities follow them quite
strictly.

Dale

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Feature request: -np (shorthand for --no-pager)

[Magnus Therning]

Ashley Coolman  writes:

> Would make sense, no?

It depends on whom you ask. I think quite a few people would argue that
short options, those with one hyphen, should consist of a single letter.
They would say that --np as shorthande for --no-pager would be better.

Personally I use command line completion to avoid having to type long
options ;)

/M

-- 
Magnus Therning  OpenPGP: 0x927912051716CE39
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe   http://therning.org/magnus

A computer never does what you want... only what you tell it.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

[git-users] Feature request: -np (shorthand for --no-pager)

[Ashley Coolman]

Would make sense, no?

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.