05-03-2019
Writing this one up for a gitlab project wiki page.
Documentation is sparse on this topic
GitLab Markdown | GitLab.
But based on how you questioned, i am guessing it is not possible to split a header line and for this one i may to live with not wrapping the line as needed per the coding guidelines of the project.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
Hi! I'm currently using AIX 5.2 and would like to know where can i find to see that there's a restriction on the number of login times a user can have. Example, I want give a 2 login per user but some one to give 3 login and some one have to give unlit login time (without logging off the... (2 Replies)
Discussion started by: herath
2 Replies
2. UNIX for Advanced & Expert Users
Hi All,
I want to insert xyz.log file in CLOB field of Oracle DB. The log file increases its size dynamically. When i am inserting the file into DB i have to check the size of the file, if its size is more than 32KB then insert upto that size into CLOB field of DB. Otherwise proceed normally.
... (1 Reply)
Discussion started by: rajeshorpu
1 Replies
3. Solaris
I get a file which has all its content in a single row.
The file contains xml data containing 3000 records, but all in a single row, making it difficult for Unix to Process the file.
I decided to insert a new line character at all occurrences of a particular string in this file (say replacing... (4 Replies)
Discussion started by: ducati
4 Replies
4. Shell Programming and Scripting
Hi
I would just like to ask if there is a way for UNIX to ignore/overcome the 255 character limit of the command line?
My problem is that I have a really long line of text from a file (300+ bytes) which i have to "echo" and process by adding commands like "sed" to the end of the line, like... (5 Replies)
Discussion started by: agentgrecko
5 Replies
5. UNIX for Dummies Questions & Answers
i have few lines:
3 4 5 6
#72 9 9 9
4 5 67 8 9
#4 6 8 92 1i want to put '#' before each line.
i used this
awk '{print "#" $0;}it gave
#3 4 5 6
##72 9 9 9
#4 5 67 8 9
##4 6 8 92 1but i want the output like this:
#3 4 5 6
#72 9 9 9
#4 5 67 8 9
#4 6 8 92 1I want to avoid the character... (5 Replies)
Discussion started by: arindam guha
5 Replies
6. Shell Programming and Scripting
Hello,
I am looking for a method to use in my bash script which allows me to use long strings with all special characters.
I have found that printf method could be helpful for me but unfortunately, when I trying
root@machine:~# tevar=`printf "%s%c"... (2 Replies)
Discussion started by: elxa1
2 Replies
7. Shell Programming and Scripting
I'm trying to create a minimal, crude keylogger for X using only a shell script. I was quickly stumped: Why do these two commands entered in a terminal emulator produce output when I type...
$ xinput test 6 | grep press
$ xinput test 6 | awk '{print $3}'
...but this command produces no... (13 Replies)
Discussion started by: DevuanFan
13 Replies
8. UNIX for Beginners Questions & Answers
cat filename| awk '{ $1=""; print $0}'
in my file there are few lines that has more than 3000 characters per line and as soon as I run the above command it cores, strings core reveals that the awk is failing because input string too long, limit. can i get some help from the experts to find... (8 Replies)
Discussion started by: knijjar
8 Replies
LEARN ABOUT OSX
git-request-pull
GIT-REQUEST-PULL(1) Git Manual GIT-REQUEST-PULL(1)
NAME
git-request-pull - Generates a summary of pending changes
SYNOPSIS
git request-pull [-p] <start> <url> [<end>]
DESCRIPTION
Generate a request asking your upstream project to pull changes into their tree. The request, printed to the standard output, begins with
the branch description, summarizes the changes and indicates from where they can be pulled.
The upstream project is expected to have the commit named by <start> and the output asks it to integrate the changes you made since that
commit, up to the commit named by <end>, by visiting the repository named by <url>.
OPTIONS
-p
Include patch text in the output.
<start>
Commit to start at. This names a commit that is already in the upstream history.
<url>
The repository URL to be pulled from.
<end>
Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled.
When the repository named by <url> has the commit at a tip of a ref that is different from the ref you have locally, you can use the
<local>:<remote> syntax, to have its local name, a colon :, and its remote name.
EXAMPLE
Imagine that you built your work on your master branch on top of the v1.0 release, and want it to be integrated to the project. First you
push that change to your public repository for others to see:
git push https://git.ko.xz/project master
Then, you run this command:
git request-pull v1.0 https://git.ko.xz/project master
which will produce a request to the upstream, summarizing the changes between the v1.0 release and your master, to pull it from your public
repository.
If you pushed your change to a branch whose name is different from the one you have locally, e.g.
git push https://git.ko.xz/project master:for-linus
then you can ask that to be pulled with
git request-pull v1.0 https://git.ko.xz/project master:for-linus
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-REQUEST-PULL(1)